Initiate credit card wallet payment in APP

Instead of redirecting your customers to the payment page in browser, you can load the payment page directly in the wallet provider app.

Integration

  • Setup callback_mobile_app_redirect config parameter

    This is the app url on the merchant's shop mobile application, where the customer will be redirected once the wallet transaction is finalized, when the transaction is done on a mobile device. This ensures that the customer does not have to switch to the browser, but rather remains in the mobile app's context, after the customer finalize the transaction.

    For more details about callback_mobile_app_redirect, please visit Payment Mobile App Redirect Page.

    Setup callback_mobile_app_redirect is optional. In case the callback_mobile_app_redirect is not set, finalize wallet payment will end up in browser and will use the callback_ok/callback_failed to show the final page.

  • Initiate credit card wallet payment in APP

    To initiate the credit card wallet payment in app, you should call the AppUrl returned from the createPaymentRequest method with some parameters.

    Example of App Url
    <?xml version="1.0"?>
<APIResponse version="20170228">
    <Header>
        <Date>2023-01-01T00:00:00+00:00</Date>
        <Path>API/createPaymentRequest</Path>
        <ErrorCode>0</ErrorCode>
        <ErrorMessage/>
    </Header>
    <Body>
        <Result>Success</Result>
        <PaymentRequestId>xyz</PaymentRequestId>
        <Url>https://<YourShopName>.altapaysecure.com/eCommerce/API/requestForm?pid=xyz</Url>
        <DynamicJavascriptUrl>https://<YourShopName>.altapaysecure.com/eCommerce/API/embeddedPaymentWindow?pid=xyz</DynamicJavascriptUrl>
        <AppUrl>https://<YourShopName>.altapaysecure.com/eCommerce/API/creditCardWalletInitiateAppPayment/xyz</AppUrl>
    </Body>
</APIResponse>

    The following parameters have to be added to the request to AppUrl. They are required for 3DSecure V2 Authentication Assessment.

    If you're unable to provide one of these parameters, safe default values will be applied. However, please be aware that using defaults may not reflect the actual application environment, which can lead to a suboptimal user experience and may even trigger 3D Secure authentication when it wouldn't otherwise be required.
    We strongly recommend providing accurate client information whenever possible to ensure smooth and consistent behavior.
    Parameter Description Type Default value
    customer_info[cardholder_name]

    Cardholder name.

    		 string
    customer_info[client_accept_language]

    The language setting of the customers browser. Used for fraud detection.

    navigator.language
    		 string en-GB
    customer_info[client_user_agent]

    The customers browser identification. Used for fraud detection.

    navigator.userAgent
    		 string Mozilla/5.0 (Linux; U; Android 10; en-US) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/89.0.4389.90 Mobile Safari/537.36
    customer_info[client_ip]

    The customers IP address. Used for fraud detection.

    		 string
    customer_info[client_accept]

    The customers browser accept header.

    		 string text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,image/apng,*/*;q=0.8
    customer_info[client_java_enabled]

    The customer's client supports java. Example: 

    navigator.javaEnabled();
    		 boolean false
    customer_info[client_color_depth]

    The customer's client screen color depth. Example: 

    screen.colorDepth;
    		 double 24
    customer_info[client_screen_height]

    The customer's client screen height. Example: 

    screen.height;
    		 double
    customer_info[client_screen_width]

    The customer's client screen width. Example: 

    screen.width;
    		 double
    customer_info[client_time_zone]

    The customer's client screen timezone. Example: 

    new Date().getTimezoneOffset();
    		 int 0
    customer_info[client_javascript_enabled]

    The customer's client supports javascript.

    		 boolean true
    Example of request
    curl --request GET \
  --url https://<YourShopName>.altapaysecure.com/merchant/API/creditCardWalletInitiateAppPayment/xyz \
  --header 'Content-Type: application/x-www-form-urlencoded' \
  --header 'Authorization: Basic auth' \
  --data 'customer_info[cardholder_name]=asdasd' \
  --data 'customer_info[client_accept_language]=en' \
  --data 'customer_info[client_user_agent]=Mozilla/5.0 (Linux; Android 13; SM-A536B)' \
  --data 'customer_info[client_ip]=172.0.0.1' \
  --data 'customer_info[client_accept]=text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.9' \
  --data 'customer_info[client_java_enabled]=false' \
  --data 'customer_info[client_color_depth]=24' \
  --data 'customer_info[client_screen_height]=845' \
  --data 'customer_info[client_screen_width]=384' \
  --data 'customer_info[client_time_zone]=-60' \
  --data 'customer_info[client_javascript_enabled]=true'

  • Redirect to APP url

    The call to /eCommerce/API/creditCardWalletInitiateAppPayment will return an APP url to the payment on the CC wallet provider APP where you should redirect the customer from you mobile app.

    Example of response
    <?xml version="1.0"?>
<APIResponse version="20170228">
    <Header>
        <Date>2023-01-09T12:36:18+00:00</Date>
        <Path>API/creditCardWalletInitiateAppPayment/202e3d20-eec0-45ce-84fa-8de5fba7e805</Path>
        <ErrorCode>0</ErrorCode>
        <ErrorMessage/>
    </Header>
    <Body>
        <Result>Redirect</Result>
        <RedirectResponse>
            <Url>mobilepayonline-test://online?paymentid=a8887637-4fca-40ba-8105-ae42c2a7b988</Url>
            <Method/>
            <Data/>
        </RedirectResponse>
    </Body>
</APIResponse>

Only MobilePay and Vipps are in scope for in-APP redirect

Known Limitation: MobilePay Subscriptions integration will NOT return an APP url on the /eCommerce/API/creditCardWalletInitiateAppPayment request, but the returned HTTPS url will redirect the customer to the MobilePay APP.